-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add OCI tags docs #52405
base: master
Are you sure you want to change the base?
Add OCI tags docs #52405
Conversation
Amplify deployment status
|
title: Oracle Cloud Tags as Teleport Agent Labels | ||
description: How to set up Teleport agent labels based on Oracle Cloud labels | ||
h1: Sync Oracle Cloud tags and Teleport agent labels |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The title uses Teleport Agent
the description and h1 use Teleport agent
. Let's be consistent across all three.
|
||
When running on an Oracle Cloud (OCI) Compute instance, Teleport will | ||
automatically detect and import the instance's freeform and defined tags | ||
as Teleport labels for SSH nodes, applications, databases, and Kubernetes clusters. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we prefer node or ssh server in user facing docs? cc @ptgott
as Teleport labels for SSH nodes, applications, databases, and Kubernetes clusters. | |
as Teleport labels for SSH servers, applications, databases, and Kubernetes clusters. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we have a preference here! Looks like the docs are pretty evenly split:
grep -REho "SSH (node|server)" docs/pages | sort | uniq -c
93 SSH node
80 SSH server
When running on an Oracle Cloud (OCI) Compute instance, Teleport will | ||
automatically detect and import the instance's freeform and defined tags | ||
as Teleport labels for SSH nodes, applications, databases, and Kubernetes clusters. | ||
Tags imported this way will have the `oracle/` prefix. | ||
|
||
When the Teleport process starts, it fetches all tags from OCI instance | ||
metadata and adds them as labels. The instance's image must support IMDSv2. | ||
The process will update the tags every hour, so newly created or deleted tags | ||
will be reflected in the labels. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we note in this section that no additional permissions are required to be granted to the OCI instance?
This change adds docs for the auto-importing of Oracle Cloud tags.
Depends on #52283.